chore(deps): update embarkstudios/cargo-deny-action action to v1.6.3#259
Merged
Merged
Conversation
| datasource | package | from | to | | ----------- | ------------------------------- | ------ | ------ | | github-tags | EmbarkStudios/cargo-deny-action | v1.5.4 | v1.6.3 |
lfrancke
approved these changes
May 14, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.4->v1.6.3Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
EmbarkStudios/cargo-deny-action (EmbarkStudios/cargo-deny-action)
v1.6.3: Release 1.6.3 - cargo-deny 0.14.21Compare Source
Fixed
cfg()/tripletargets could cause features to be resolved incorrectly and thus crates to be not pulled into the graph used for checking.[0.14.20] - 2024-03-23
Fixed
gix-transport(and its unique dependencies) to 0.41.2 as a workaround forcargo installnot using the lockfile. See this issue for more information.v1.6.2: Release 1.6.2 - cargo-deny 0.14.19Compare Source
Changed
--locked.[0.14.18] - 2024-03-21
Fixed
krates.[0.14.17] - 2024-03-17
Changed
gix-> 0.60.v1.6.1Compare Source
Fixed
v1.6.0Compare Source
action changes
0.14.15
Added
infoor higher to make the diagnostic clearer by default.0.14.14
Fixed
0.14.13
Fixed
bansdiagnostic codes could not have their lint level changed via the CLI. It also introduced thedeprecateddiagnostic code.0.14.12
Changed
targets,exclude,all-features,features,no-default-features, andexcludeinto the[graph]table.feature-depthinto the[output]table.Added
advisories.db-path, which expands support beyond just~to include environment variable expansion.Fixed
tomlandserdewithtoml-span.name = "<crate_name>", version = "<requirements>"used to target specific crates into either a plain package spec string or the simplercrate = "<package spec>".reason = "<reason>"field to many fields within the configuration that are provided in diagnostics.[bans.deny]also has an additionaluse-instead = "<url/crate_name>". PR#610 did this for theadvisories.ignorefield.[advisories.ignore]array.Deprecated
[advisories]vulnerabilityunmaintainedunsoundnoticeseverity-threshold[licenses]unlicensedallow-osi-fsf-freecopyleftdefaultdenyv1.5.15: Release 1.5.15 - cargo-deny 0.14.11Compare Source
Fixed
v1.5.14: Release 1.5.14 - cargo-deny 0.14.11Compare Source
Added
manifest-pathkey as a shorthand for doingarguments: --manifest-path <path>v1.5.13: Release 1.5.13 - cargo-deny 0.14.11Compare Source
Fixed
v1.5.12: Release 1.5.12 - cargo-deny 0.14.10Compare Source
Fixed
kratesagain to pull in krates#77.v1.5.11: Release 1.5.11 - cargo-deny 0.14.9Compare Source
Fixed
kratesagain to pull in krates#75.v1.5.10: Release 1.5.10 - cargo-deny 0.14.8Compare Source
Fixed
kratesagain to pull in krates#73.v1.5.9: Release 1.5.9 - cargo-deny 0.14.7Compare Source
Fixed
kratesagain to pull in krates#71.v1.5.8: Release 1.5.8 - cargo-deny 0.14.6Compare Source
Fixed
kratesto fix an issue with crates that directly have a dependency on 2 or more versions of the same crate.Added
wrappercrate for a banned crate does not have a dependency on that crate.Changed
gixandtame-index.v1.5.7: Release 1.5.7 - cargo-deny 0.14.5Compare Source
Fixed
v1.5.6: Release 1.5.6 - cargo-deny 0.14.4Compare Source
Fixed
v1.5.5: Release 1.5.5 - cargo-deny 0.14.2Compare Source
Added
bans.buildconfiguration option, opting in to checking for file extensions, native executables, and interpreted scripts. This resolved #43.Changed
dev-dependenciesare handled. By default, crates that are only used as dev-dependencies (ie, there are no normal nor build dependency edges linking them to other crates) will no longer be considered when checking formultiple-versionsviolations. This can be re-enabled via thebans.multiple-versions-include-devconfig field. Additionally, licenses are no longer checked fordev-dependencies, but can be re-enabled vialicenses.include-devthe config field.dev-dependenciescan also be completely disabled altogether, but this applies to all checks, includingadvisoriesandsources, so is not enabled by default. This behavior can be enabled by using theexclude-devfield, or the--exclude-devcommand line flag. This change resolved #322, #329, #413 and #497.Fixed
native-certsfeature flag that can enable the OS native certificate store.Deprecated
bans.allow-build-scriptstobans.build.allow-build-scripts.bans.allow-build-scriptsis still supported, but emits a warning.Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.